======================================================================
  Microsoft(R) Product Support Services Application Note (Text File)
                       WG0949: SETUP INFORMATION
======================================================================
                                                  Revision Date: 11/93
                                                      No Disk Included

The following information applies to Microsoft Windows for Workgroups,
version 3.11.

-----------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY     |
| ACCOMPANY THIS DOCUMENT (collectively referred to as an Application |
| Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER      |
| EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED      |
| WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR       |
| PURPOSE. The user assumes the entire risk as to the accuracy and    |
| the use of this Application Note. This Application Note may be      |
| copied and distributed subject to the following conditions:  1) All |
| text must be copied without modification and all pages must be      |
| included;  2) If software is included, all files on the disk(s)     |
| must be copied without modification (the MS-DOS(R)  utility         |
| diskcopy is appropriate for this purpose);  3) All components of    |
| this Application Note must be distributed together;  and  4) This   |
| Application Note may not be distributed for profit.                 |
|                                                                     |
| Copyright (C) 1993 Microsoft Corporation.  All Rights Reserved.     |
| Microsoft and MS-DOS are registered trademarks and Windows and      |
| Windows NT are trademarks of Microsoft Corporation.                 |
| Artisoft and LANtastic are registered trademarks of Artisoft, Inc.  |
| AT&T is a registered trademark of American Telephone and Telegraph  |
| Company.                                                            |
| Banyan and VINES are registered trademarks of Banyan Systems, Inc.  |
| DEC is a registered trademark and Pathworks is a trademark of       |
| Digital Equipment Corporation.                                      |
| TCS is a registered trademark of Eurotherm International P.L.C.     |
| IBM and OS/2 are registered trademarks of International Business    |
| Machines Corporation.                                               |
| NetWare and Novell are registered trademarks of Novell, Inc.        |
| Olivetti is a registered trademark of Ing. C. Olivetti.             |
| PC-NFS and Sun Microsystems are registered trademarks of Sun        |
| Microsystems, Incorporated.                                         |
|---------------------------------------------------------------------|
                                      
                               
                           TABLE OF CONTENTS
                           =================
                                   
                                   
                             INTRODUCTION
                             ============

This Application Note discusses installation requirements for
Microsoft Windows for Workgroups version 3.11, the differences between
the Setup programs for Windows for Workgroups 3.11 and Microsoft
Windows operating system 3.1, new device drivers and files that ship
with Windows for Workgroups, and the Setup options /A, /N, and /H.
                                   
                                   
                       INSTALLATION REQUIREMENTS
                       =========================

To install and use Windows for Workgroups 3.11, you must be using MS-
DOS version 3.3 or later. To upgrade from a previous installation of
Windows, your Windows version must be 3.1 or later, and your Windows
files must be included in your PATH statement. (If you have a version
of Windows earlier than 3.1, you need to do a complete Windows for
Workgroups installation, not an upgrade.) If you want to preserve your
Program Manager groups and other existing Windows settings, you need
to install Windows for Workgroups in the directory of your current
Windows installation.

DISK SPACE REQUIREMENTS
=======================

Windows for Workgroups 3.11 requires approximately 4.5 megabytes (MB)
more disk space than Windows 3.1. The following table illustrates the
disk space requirements for the most common installation types.

Type of Installation          Windows 3.1    Windows for Workgroups 3.11
------------------------------------------------------------------------                                      
Full installation (286)            8.6 MB         Not Available
Upgrade 3.x (286)                  5.2 MB         Not Available
Full installation (386)            9.5 MB               18.0 MB
Upgrade 3.x (386)                  5.2 MB                9.0 MB
Network administrator (setup /A)  15.3 MB               21.0 MB 
Network setup (setup /N)            .3 MB                1.2 MB

SUPPORTED NETWORKS
==================

The following networks are supported for use with Windows for
Workgroups 3.11:

 - Artisoft(R) LANtastic(R) (versions 3.x, 4.x, and 5.x)
 - Banyan(R) VINES(R) (versions 4.11, 5.0, and 5.52)
 - BW-NFS (version 3.0)
 - DEC(R) Pathworks(TM) (versions 4.0, 4.1, and later)
 - IBM(R) OS/2(R) Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0
   without API)
 - Microsoft LAN Manager (version 2.1)
 - Microsoft Windows Network
 - Microsoft Windows NT(TM) (version 3.1)
 - Microsoft Workgroup Client (all versions)
 - Novell(R) NetWare(R) (versions 3.x, 4.0, and later)
 - Sun Microsystems(R) PC-NFS(R) (version 5)
 - TCS(R) 10Net (versions 4.1x, 4.2, and 5.0)

Before you run a shared copy of Windows for Workgroups that is
installed over one of these networks, read the following guidelines.
For some networks, you need to take some preliminary steps before
running a shared copy of Windows for Workgroups.

Novell NetWare Network
----------------------

If you are running a shared copy of Windows for Workgroups on a Novell
workstation, be sure to log on to the Novell server before starting
Windows for Workgroups.

Microsoft LAN Manager and Windows for Workgroups
------------------------------------------------

Before you run a shared copy of Windows for Workgroups on a LAN
Manager or Windows for Workgroups workstation, be sure to start the
network workstation services. You can do this with the NET START
WORKSTATION command.

If you are using the Windows for Workgroups network drivers, you can
start the workstation services automatically by placing one of the
following entries in the [Network] section of your SYSTEM.INI file:

   autostart=full
   autostart=basic

Setting AUTOSTART to FULL installs the enhanced network redirector.
The enhanced redirector supports named pipes and LAN Manager
application programming interface (API) functions.

Setting AUTOSTART to BASIC installs the basic network redirector,
which uses less system memory but does not support named pipes.

Neither redirector supports network messaging services or pop-up
messages.

LAN Manager automatically installs the redirector based on entries in
your AUTOEXEC.BAT and CONFIG.SYS files. These settings are specified
in the LAN Manager network documentation.

  NOTES
  
   - With Windows for Workgroups 3.11, you can connect to and use files,
     directories, and printers that are shared on a Microsoft Windows NT
     or a Microsoft LAN Manager server. To view the name of a LAN
     Manager server, at least one computer on the network must have a
     workgroup name that matches the name of the primary domain of the
     LAN Manager server.
 
   - Unlike in version 3.1, if you are running a shared copy of Windows
     for Workgroups 3.11, you cannot share your workstation's resources
     once you have started the real mode redirector.

Using Windows for Workgroups with a Different Network Operating System
----------------------------------------------------------------------

In addition to the Windows for Workgroups 3.11 network functionality,
you can install Windows support for a third-party network operating
system. The network operating systems currently supported are:

 - Banyan VINES (versions 4.11, 5.00, and 5.52)
 - BW-NFS (version 3.0)
 - Novell NetWare Shell (versions 3.x and 4.x)
 - Sun Microsystems PC-NFS (version 5.0)

No third-party files are included with Windows for Workgroups 3.11.
You must obtain all third-party network operating system files from
your network vendor. You must install the third-party network
operating system before you select the Windows support option.

   NOTE: This procedure is not useful unless the drivers you obtain
   from your vendor are compatible with Windows for Workgroups.

To use Windows for Workgroups with a different network:

1. In the Network group in Program Manager, choose the Network Setup
   icon.

2. In the Network Setup dialog box, choose the Networks button.

   The Compatible Networks dialog box appears.

3. Select the Other option button under the heading "You can install
   Windows support for an additional network" and then select the
   network you want to set up. If that network does not appear in the
   list, select Unlisted Or Updated Network.

   You are then prompted to insert the disk containing the network
   driver supplied by your vendor. After you insert the floppy disk in
   your drive, Setup installs the network driver. The new network
   should then appear in the Available Network Types group.
   
4. Select your network and choose the Add button.

   This adds the network to the Other Networks In Use list.

5. Choose the OK button twice to exit the Network dialog boxes.

     IMPORTANT: To use the new driver(s), you must reboot your machine.

INSTALLING WINDOWS SUPPORT FOR A THIRD-PARTY NETWORK ONLY
=========================================================

You can install Windows support for a third-party network only;
however, you lose Windows for Workgroups peer-to-peer functionality if
you do so. You can install support for the following networks:

 - Artisoft LANtastic (versions 3.x, 4.x, and 5.x)
 - Banyan VINES (versions 4.11, 5.0, and 5.52)
 - BW-NFS (version 3.0)
 - DEC Pathworks (versions 4.0, 4.1, or later)
 - IBM OS/2 Lan Server (versions 1.2, 1.3, 1.3 CSD, and 2.0 without API)
 - Microsoft Windows Network (version 3.11 Basic)
 - Novell NetWare (versions 3.x, 4.0, and later)
 - Sun Microsystems PC-NFS (version 5)
 - TCS 10Net (versions 4.1x, 4.2, and 5.0)
                                   
                                   
                   DIFFERENCES IN SETUP PROGRAMS FOR
                   =================================
              WINDOWS 3.1 AND WINDOWS FOR WORKGROUPS 3.11
              ===========================================

This section discusses new features in the Windows for Workgroups
Setup program, including network detection and dialog box changes.

NETWORK DETECTION
=================

 - Windows for Workgroups 3.11 Setup performs network card detection.
   If Setup fails to detect your network card, it prompts you to
   choose from a list of available network adapters.

 - After a failed installation attempt, you can also force Setup to
   perform network card detection by using the /F switch (setup /F).

 - You can select No Network as a network type during Setup.


DIALOG BOXES
============

 - Windows for Workgroups Setup 3.11 asks for the computer name and
   the workgroup in the initial user name dialog box.

 - After Setup completes printer installation, the Install New Network
   Adapter, Network Adapters, and Compatible Networks dialog boxes may
   appear, as the following table illustrates.

   Dialog box                    Express Setup    Custom Setup
-----------------------------------------------------------------
   Install New Network Adapter   Conditional      Conditional
   Network Adapters              No               Yes
   Compatible Networks           Conditional      Yes

   The Install New Network Adapter dialog box does not appear during
   either Express or Custom Setup if the Network Card Detection (NCD)
   utility detects your network card and you confirm the detected
   network card. Confirming the detected network card places a network
   adapter entry in the PROTOCOL.INI file. If you don't confirm the
   detected network card, the Install New Network Adapter dialog box
   appears. If you are upgrading from a Workgroup Connection or LAN
   Manager 2.1 installation, there is already a valid network adapter
   entry in the PROTOCOL.INI file, and this dialog box is skipped.
   
   The Compatible Networks dialog box does not appear during Express
   Setup if you are upgrading from a LAN Manager 2.1 installation.
   Selecting a network in this dialog box places a multinet= entry in
   the [Network] section of the SYSTEM.INI file. If Setup detects the
   existing LAN Manager 2.1 installation, Setup places the multinet=
   entry in the SYSTEM.INI file and therefore skips the Compatible
   Networks dialog box.

 - Once Setup is complete, the option to restart Windows is no longer
   available. (To load or upgrade network drivers, you must reboot
   your machine.)
                                   
                                   
      DRIVERS AND FILES SHIPPED WITH WINDOWS FOR WORKGROUPS 3.11
      ==========================================================

Setup does not delete drivers that were installed with Windows 3.1 but
were not shipped with Windows for Workgroups. The following table
shows the drivers and files that do ship with Windows 3.1 and/or
Windows for Workgroups.

Driver or file               Windows 3.1    Windows for Workgroups 3.11
-----------------------------------------------------------------------
Quad video driver               Yes         No

ATI VIP video driver            Yes         No

82C441 video driver             Yes         No

ET 4000 video driver            No          Yes--however, Windows for
                                            Workgroups does not detect
                                            this display. You must
                                            manually select the driver.

Olivetti(R)/AT&T(R)             Yes         No
Keyboard Mouse driver

MSCDEX CD-ROM driver            Yes         Yes--updated. If there is
and TBMI2.COM file                          an existing MSCDEX driver
                                            or TBM12.COM file, Setup
                                            copies the new driver and
                                            file to the Windows
                                            directory and modifies the
                                            AUTOEXEC.BAT file to point
                                            to the new (updated) driver
                                            and file.

WFWNET.DRV                      No          Yes

VNETBIOS.386                    No          Yes

VNETSUP.386                     No          Yes

VREDIR.386                      No          Yes

VSERVER.386                     No          Yes

VBROWSE.386                     No          Yes

VWC.386                         No          Yes

NETAPI.DLL                      No          Yes

PMSPL.DLL                       No          Yes

NETDDE.EXE                      No          Yes

NDDENB.DLL                      No          Yes

WFWSETUP.CPL                    No          Yes

NETWORK.INF                     No          Yes

LM21DRV.UPD                     No          Yes

WFWNET.HLP                      No          Yes

CLIPSRV.EXE (ClipBook server)   No          Yes

CLIPBRD.EXE (ClipBook Viewer)   No          Yes

WINCHAT.EXE (Chat)              No          Yes

WINMETER.EXE (WinMeter)         No          Yes

MSMAIL.EXE (Mail)               No          Yes

SCHDPLUS.EXE (Schedule)         No          Yes

NETWATCH.EXE (NetWatcher)       No          Yes

MSHEARTS.EXE (Hearts)           No          Yes

CALENDAR.EXE (Calendar)         Yes         No

SSMYST.SCR (Mystify             Yes         No
screen saver)

ARCHES.BMP (Arches wallpaper)   Yes         No

CHITZ.BMP (Chitz wallpaper)     Yes         No

FLOCK.BMP (Flock wallpaper)     Yes         No

MARBLE.BMP (Marble wallpaper)   Yes         No

TARTAN.BMP (Tartan wallpaper)   Yes         No

CHORD.WAV (Chord sound)         Yes         No

TADA.WAV (Trumpet sound)        Yes         No

APPS.HLP (Application           Yes         No
Compatibility Help)

COMMCTRL.DLL                    No          Yes

FRAMEWRK.DLL                    No          Yes

MAILMGR.DLL                     No          Yes

MAILSPL.EXE                     No          Yes

MAPI.DLL                        No          Yes

MSSFS.DLL                       No          Yes

PABNSP.DLL                      No          Yes

DEMILAYR.DLL                    No          Yes

SENDFILE.DLL                    No          Yes

STORE.DLL                       No          Yes

VFORMS.DLL                      No          Yes

AB.DLL                          No          Yes

NDDEAPI.DLL                     No          Yes

VSHARE.386                      No          Yes

VCD.386                         Yes         Yes

VDMAD.386                       Yes         Yes

VPICD.386                       Yes         Yes

VPD.386                         Yes         Yes

                                   
           SETUP OPTIONS (SETUP /A, SETUP /N, AND SETUP /H)
           ================================================

SETUP /A AND SETUP /N
=====================

You run Setup with the /A and /N options to configure a workstation to
run Windows from a shared directory. Administrative Setup (setup /A)
copies all the files from the Windows distribution disks to a single
directory and marks them as read-only. This directory can then be used
to install and run a shared copy of Windows. Setup /N sets up the
shared copy of Windows.

In a stand-alone Windows 3.1 installation, the Windows directory and
SYSTEM subdirectory are on your personal hard disk drive. In a shared
Windows installation, the Windows directory can be located on the
user's hard disk drive or on a network drive, and can be customized
for each user. There is no SYSTEM subdirectory, as such, in a network
installation; system files are typically located in a shared directory
on a network server.

In Windows for Workgroups 3.11, as in Windows 3.1 running on a
network, the personal Windows directory contains all files with .INI,
GRP, and .PIF extensions, as well as REG.DAT, WIN.COM, WINVER.EXE, and
any MS-DOS device driver files. The personal Windows directory may
also contain the MS-DOS network device drivers and the NET.EXE,
MSIPX.COM, and NETX.COM files. (These files may also be copied to the
root directory of the boot drive, as explained in the following
section.) The shared directory contains all other Windows files.

   NOTE: If you are setting up a third-party network operating system
   under Windows for Workgroups, you must place the necessary files
   provided by the third-party network operating system manufacturer
   in the shared Windows directory created by the setup /a command.
   When you run setup /n, Setup does not prompt you for these files.

Where Setup Places Network Files
--------------------------------

The Windows 3.1 Setup program reads the SETUP.INF file to determine
where to install files. SETUP.INF uses the file classifications WINDIR
and SYSDIR to refer to files that Setup installs in the Windows
directory and SYSTEM subdirectory, respectively.

The Windows for Workgroups 3.11 Setup program reads the NETWORK.INF
file to determine where to install files. Setup places files with the
windir classification in the personal Windows directory and files with
the sysdir classification in a shared server directory. NETWORK.INF
also uses two new file classifications, NETDIR and DEVDIR. Where Setup
places these files depends on the type of installation.

Real-mode network device drivers (devdir files) are copied to the
personal Windows directory on a local nonremovable, noncompressed
drive. These include PROTMAN.DOS, PROTOCOL.INI, and WORKGRP.SYS. If
the personal Windows directory is on a remote, removable, or
compressed volume, then these files are copied to the root of the boot
drive. These device drivers must be correctly referenced in the
CONFIG.SYS file.

Real-mode network utilities and terminate-and-stay-resident (TSR)
programs (netdir files) are copied to the personal Windows directory
on a nonremovable hard disk. These include NET.EXE, MSIPX.COM,
NETX.COM, and ROUTE.COM. If the personal Windows directory is on a
remote or removable volume, these files are copied to the same
directory as the devdir files. These utilities and TSRs must be
correctly referenced in the AUTOEXEC.BAT file.

   NOTE: If your personal Windows directory is on a remote volume, you
   still must have your own hard disk drive to run Windows for
   Workgroups. Windows for Workgroups does not support diskless
   workstations or systems without hard disk drives.

The following table illustrates where Setup places the netdir and
devdir files for different installations.

                                          Location of   Location of
Location of Windows installation          netdir files  devdir files
--------------------------------------------------------------------
Nonremovable hard disk drive              Windows       Windows
Compressed nonremovable hard disk drive   Windows       Root
Removable drive (for example, SCSI)       Root          Root
Remote drive (setup /N)                   Root          Root

BATCH MODE SETUP (SETUP /H)
===========================

You can use Setup with the /H option to automate the Setup program.
Windows for Workgroups 3.11 and Windows 3.1 come with a system-
settings template file called SETUP.SHH, which you can copy or modify
to create a custom system-settings file. In addition to the settings
specified in the Windows 3.1 template file, the Windows for Workgroups
template file includes parameters for the computer name, workgroup,
network card, protocol, and compatible network. The SETUP.SHH file is
located on Windows for Workgroups 3.11 Disk 1 and is copied to the
shared Windows for Workgroups directory when you run setup /A. You can
modify the template file with any text editor that can save
unformatted text (ASCII) files.

For more information about batch mode setup, refer to Chapter 3 of the
Microsoft Windows for Workgroups "Resource Kit."